Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

retry ssh run in e2e tests #2788

Merged
merged 3 commits into from
Mar 22, 2023
Merged

retry ssh run in e2e tests #2788

merged 3 commits into from
Mar 22, 2023

Conversation

nagworld9
Copy link
Contributor

Description

retry ssh run in e2e tests

Issue #


PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • If applicable, the PR references the bug/issue that it fixes in the description.
  • New Unit tests were added for the changes made

Quality of Code and Contribution Guidelines

@codecov
Copy link

codecov bot commented Mar 20, 2023

Codecov Report

Merging #2788 (660454d) into develop (1640510) will not change coverage.
The diff coverage is n/a.

❗ Current head 660454d differs from pull request most recent head 4e68cf3. Consider uploading reports for the commit 4e68cf3 to get more accurate results

@@           Coverage Diff            @@
##           develop    #2788   +/-   ##
========================================
  Coverage    71.99%   71.99%           
========================================
  Files          104      104           
  Lines        15857    15857           
  Branches      2273     2273           
========================================
  Hits         11417    11417           
  Misses        3915     3915           
  Partials       525      525           

see 1 file with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

# Instance of 'Exception' has no 'exit_code' member (no-member) - Disabled: e is actually an CommandError
if e.exit_code != 255 or attempts == 0: # pylint: disable=no-member
raise
log.warning("The operation failed with SSH Connection time out, retrying in 30 secs. Error: %s", e)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we log the actual stderr instead of "failed with SSH Connection time out,"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

narrieta
narrieta previously approved these changes Mar 21, 2023
maddieford
maddieford previously approved these changes Mar 22, 2023
@nagworld9 nagworld9 merged commit a78787b into Azure:develop Mar 22, 2023
@nagworld9 nagworld9 deleted the retry-ssh-run branch March 22, 2023 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants